-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Fix Azure DevOps checkout step in the courtesy-push.js file #21204
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…eation, avoid pushing changes to the feed
…c to avoid CG issues
/azp run |
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
tarunramsinghani
approved these changes
Aug 11, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
Fix the issue in the previous PR: #21200
Failed pipeline run link: https://dev.azure.com/mseng/AzureDevOps/_build/results?buildId=30323883&view=logs&s=7cadbae7-7533-548a-becd-a2da10fc0146
Task Name
NA
Description
Key changes include:
Risk Assessment (Low / Medium / High)
Low
Change Behind Feature Flag (Yes / No)
No because this is a release pipeline.
Tech Design / Approach
The original pipeline approach included AzureDevOps repository as a pipeline resource, which created CG dependency conflicts. Additionally, there was no safe testing mechanism for validating the entire workflow without external side effects.
Changes made:
Documentation Changes Required (Yes/No)
Yes.
Added a new paramter dryRun in the courtesy push pipeline.
Image:

Unit Tests Added or Updated (Yes / No)
No - This is an internal refactor of existing functionality. The courtesy push logic remains functionally equivalent, and comprehensive testing will be performed through integration testing in the pipeline environment
Additional Testing Performed
Locally tested:
Logging Added/Updated (Yes/No)
Yes
Link: https://dev.azure.com/surajitshil/Azure-Repo-File-Structure/_build/results?buildId=289&view=logs&j=12f1170f-54f2-53f3-20dd-22fc7dff55f9&t=9c939e41-62c2-5605-5e05-fc3554afc9f5
Telemetry Added/Updated (Yes/No)
No
Rollback Scenario and Process (Yes/No)
NA
Dependency Impact Assessed and Regression Tested (Yes/No)
NA
Checklist
NA